The Remote Desktop license server isn't available when you connect to an Azure VM

This article helps resolve the issue when you can't connect to an Azure virtual machine (VM) because no Remote Desktop license server is available to provide a license.

When you try to connect to a VM, you may encounter the following scenarios:

The VM screenshot shows that the operating system is fully loaded and waiting for credentials.

You receive the following error messages when you try to make a Microsoft Remote Desktop Protocol (RDP) connection:

The remote session was disconnected because there are no Remote Desktop license servers available to provide a license.

No Remote Desktop license server is available. Remote Desktop Services will stop working because this computer is past its grace period and hasn't contacted at least a valid Windows Server 2008 license server. Select this message to open RD Session Host Server Configuration to use Licensing Diagnosis.

A licensing error occurred while the client was attempting to connect (Licensing timed out). Please try connecting to the remote computer again.

The RDP connection appears to be stuck in the "Configuring remote session" status.

This problem occurs if a Remote Desktop license server is unavailable to provide a license to start a remote session. It can be caused by several scenarios, even though a Remote Desktop Session Host role was set up on the VM:

To resolve this problem, back up the OS disk and follow these steps:

Connect to the VM by using an administrative session. To do this, use one of the following ways:

Run the following command:

In the Azure portal, go to the VM, select Connect under Settings. In the right panel, select Download RDP File to download a connection file.

If you can't connect to the VM by using an administrative session, you can use the Virtual Machine Serial Console on Azure to access the VM as follows:

Access the Serial Console by selecting Support & Troubleshooting > Serial console. If the feature is enabled on the VM, you can connect the VM successfully.

Create a new channel for a CMD instance. Enter CMD to start the channel and get the channel name.

Switch to the channel that runs the CMD instance. In this case, it should be channel 1:

Select Enter again and enter a valid username and password, local or domain ID, for the VM.

Check whether the VM has a Remote Desktop Session Host role enabled. If the role is enabled, make sure that it's functioning properly. Open an elevated CMD instance and follow these steps:

Use the following command to check the status of the Remote Desktop Session Host role:

If this command returns a value of 0, it means that the role is disabled, and you can go to step 3.

Use the following command to check the policies and reconfigure as needed:

If the LicensingMode value is set to any value other than 4, per user, then set the value to 4:

If the SpecifiedLicenseServers value doesn't exist, or it has incorrect license server information, then change it as follows:

After you make any changes to the registry, restart the VM.

If you don't have CALs or you don't need more than two concurrent users, remove the Remote Desktop Session Host role. Then RDP will be set back to allow only two concurrent RDP connections to the VM:

If the VM has the Remote Desktop licensing role and it isn't used, you can also remove that role:

Make sure that the VM can connect to the Remote Desktop license server. You can test the connectivity to the port 135 between the VM and the license server:

If there's no Remote Desktop license server in the environment and you want one, you can install a Remote Desktop licensing role service. Then configure the RDS licensing.

If a Remote Desktop license server is configured and healthy, make sure that the Remote Desktop license server is activated with CALs.

If you have questions or need help, create a support request, or ask Azure community support. You can also submit product feedback to Azure community support.